…g installation

This is meant to be used in tests which currently suffer from huge import
resolution conflicts. Instead of letting fixtures and test code attempt to
import the same files (and failing to do so), we should just pack the CLI
and let it output the project structure. This makes it possible to test
project parsing in real world scenarios, since even the devdeps of the CLI
will not be resolvable (which so far has prevented things like proper
testing for the file loaders).

In order to make project parsing work without authentication, the PW code
bundle upload was separated into a different bundle. Both the deploy and test
commands were updated to support this. As a result they are now able to report
more accurate status since the upload is separate from bundling, and the
new project parsing command doesn't need authentication.

TODO: Local code bundles are no longer getting cleaned up (deleted) after
they have been uploaded. This needs fixing.

…y became an issue

The proxy utility is now in a separate file which gets rid of the circular dep.
There may be more but for now this fixes the issue.

Files above the workspace root are not bundleable.

It's not relevant and it messes up paths.

Instead of relying on memory and dependencies being shared between the CLI and
test fixtures, which leads to various issues, we add new debug commands to the
CLI that allow us to inspect the state of a fixture or file. We inspect
the output of the command instead of relying on shared memory.

Various changes were required to make this work.

…n to keep it fresh

…to deploy, test)

… pw-test e2e tests work

…acked archive

…ing a larger runner

… npm install